2015-10-21 - 22459 - Service Request - Cancellation Code in OSA500 Not Working #CrystalReportsSupport
Service Request
22459.200 - Cancellation Code in OSA500 Not Working
Problem Summary
Need to fix adding Cancellation code in OSA500 does not update the report accordingly.
Admin Info
Purpose
|
Need to fix adding Cancellation code in OSA500 does not update the report accordingly.
|
Requested by
|
Jayne Palfreman
|
Issue Date
|
10-21-2015
|
Resolved by
|
Dhananjay G
|
Resolved Date
|
10-28-2015
|
Document Status
|
Complete
|
Detailed Problem Description
EMail from Jayson Osmars on 10/21/2015:
Some background, the Cancellation code prompt on OSA500 (EMEA in particular) is only delivering result for "ALL". If they want a code 'ZF' for example there's no data.
What I noticed was the BEX isn't pulling all the data, just the summed result. It may need a LOV, or a hierarchy or static list associated to it.
Solution Analysis and Recommendations
1. Need to analyze the issue in OSA500 report in BI Production.
2. Need to maintain the LOV's for Rejection Reason Code and Fiscal Period parameters in report for all Global & Regional versions based on master data.
3. Need to maintain LOV's for both prompts in OSA500 Global & Regional versions is as below file :
Rejection Reason Codes VS Fiscal Period LOVs.txt
4. Need to validate the report versions with BEx queries after completing the development changes.
5. Need to design all regional versions of OSA500 report.
6. Need to create the Sales Org parameter at the report level for regionalizing all versions of OSA500 report.
Test Plan
Test ID
|
Test Scenario
|
Expected Results
|
1
|
Report Format.
|
Should be as per NEC crystal standard checklist.
|
2
|
Execute Crystal Report in Crystal Designer tool after changes.
|
Report should execute successfully in Crystal Designer tool.
|
3
|
Schedule the Report in NEC BI Launch Pad.
|
Report should execute successfully in NEC BI Launch Pad.
|
Resolution
1. Analyzed the issue on OSA500 report in BI Production.
2. Maintained the LOV's for Reason Code and Fiscal Period parameters in report for all Global & Regional versions based on master data.
3. Validated the OSA500 report all versions with BEx queries after completing the development changes.
4. Designed the all regional versions of OSA500 report.
5. Created the Sales Org parameter at the report level for regionalizing all versions of OSA500 report.
Release Information
None